Method for the provision of location information

ABSTRACT

In a communication system a request for location information associated with a target user is signalled from an entity. Said request contains information identifying the requestor of said location information. A verification is performed based on said identifying information if the target user has authorised the requester to initiate provision of location information that associates with the target user. The location provision is initiated if it is determined that the requester is authorised by the target user to initiate provision of location information that associates with the target user.

FIELD OF THE INVENTION

The present invention relates to provision of location information bymeans of a communication system.

BACKGROUND OF THE INVENTION

Communication systems providing mobility for the users thereof areknown. A well known example of the mobile communication systems is thepublic land line mobile network (PLMN), a cellular communication networkbeing an example of the PLMN. Another example is a mobile communicationsystem that is based, at least partially, on use of communicationsatellites.

The mobile network apparatus and/or user equipment such as a mobilestation can be employed for provision of information regarding thegeographical location of the user equipment and thus the user thereof. Amobile user equipment and thus the user thereof can be positioned byvarious different techniques. For example, substantially accurategeographical location information that associates with a user equipmentcan be obtained based on the known satellite based GPS (GlobalPositioning System). More accurate location information can be obtainedthrough a differential GPS.

Another possibility is to use a location service that associates with acellular telecommunications system for the provision of the locationinformation. In this approach the cells or similar geographicallylimited radio access entities and associated controllers of thecommunication system are utilised in production of at least a roughlocation information estimate concerning the current location of themobile user equipment. To improve the accuracy of the locationinformation the communication system may be provided with specificlocation measurement units that provide more accurate data concerningthe location of a user equipment within the service area of the cellularsystem. It is also possible to conclude geographical location when themobile user equipment is located within the coverage area of a visitedor “foreign” network. The visited network may be made capable oftransmitting the location of the mobile user equipment back to the homenetwork, e.g. to support services that are based on location informationor for the purposes of routing and charging. The production of data forthe location determinations does not form an essential element of thepresent invention, and is thus not described in any greater detailherein.

The location data may be processed in a specific location service entitythat is implemented either within the cellular system or connectedthereto. The location data may also be processed in the user equipmentthat is provided with appropriate processing capacity. The locationservice entity provided by the communication system may serve differentclients via an appropriate interface.

The location information may be used for various purposes, such as forlocation of a mobile telephone that has made an emergency call, forlocating vehicles or given mobile subscribers and so on. In general, aclient such as a user equipment or another entity wishing to receivelocation information regarding a user equipment may send a request forsuch information to the location service provision entity. The locationservice provisioning entity will then process the request, obtain therequired data and generate an appropriate response.

An example of the provision of the location information by a PLMN isdescribed in more detail 3^(rd) Generation Partnership Project (3GPP)technical specifications, see e.g. 3GPP TS 23.271 version 4.2.0, titled“Functional stage 2 description of LCS”, June 2001.

According to the 3GPP specification a location service (LCS) serverentity referred to as a Gateway Mobile Location Center (GMLC) isprovided for managing the location services. The GMLC is for gatheringand storing various data that may be used in provision of locationinformation for location service clients (LCS clients).

The LCS Client may make use of that location information for variousservices/applications. A possible application comprises a LCS clientarranged to provide location information in response to a request fornon-call related location information. Such a request for locationinformation is referred to in the 3GPP specifications as a non-callrelated MT-LR (Mobile Terminated Location Request).

Use of a so called “Authorized UE List” has been proposed. This listcontains Mobile Subscriber ISDN (MSISDN) numbers or groups of MSISDNswhich are authorised to initiate a location information provisionprocedure. That is, MSISDNs or groups of MSISDN are listed for which theLCS Client may issue a non-call related MT-LR. Separate lists of MSISDNsmay be associated with each distinct external or non-call related clientidentity. Location information may be provided by the LCS server to theLCS client in response to a request for location information from a userwith a MSISDN number that appears in said list.

The LCS Client who is external to the PLMN system may only be enabled tovalidly issue location information requests for those MSISDNs which arefound on the “Authorized UE List”. That is, the LCS clients request mayonly be responded for subscribers who subscribe to the location servicesprovided by the PLMN, as their MSISDNs would not otherwise appear on thelist.

Request from the LCS Client are authenticated based on a combination ofa Client ID and password stored in a LCS Client profile at the LSCserver (e.g. the GMLC) and authorized based on the “Authorized UE List”.That is, the LCS client is authorised to receive location informationfrom the GMLC entity if the requesting user equipment (UE) is found fromthe list.

The inventors have found that there is no mechanism for the targetmobile user equipment, and more particularly, to the user thereof, toselectively prevent provision of information about their location. Theusers may not select provision of a certain location service application(or certain applications) and at the same time restrict any such partiesthat are allowed by the location service system to request for locationinformation regarding any other user equipment.

A simple example of this type of service is the so called “Friends Find”application. In here a target user cannot control the users who areallowed to receive location information about the target users location.A request for location information may not be rejected if the LCS clientis allowed to receive the location information from the LCS server.

However, the inventors believe that there is a need for a solution bymeans of which a user of a target user equipment could select to who areauthorised to receive such information and to be able to preventprovision of location information to any unwanted requesters.

Furthermore, LCS clients are typically Application Service Providers(ASP) who are not a part of the PLMN system. Therefore the operator ofthe PLMN may not be able to control the behaviour of the LCS client.This may cause security concerns among subscribers who have privacyconcerns and who would like to restrict the accessibility to locationdata associated with them.

SUMMARY OF THE INVENTION

Embodiments of the present invention aim to address one or several ofthe above problems.

According to one aspect of the present invention, there is provided amethod in a communication system, the method comprising: signalling arequest for location information associated with a target user, saidrequest containing information identifying the requestor of saidlocation information; verifying based on said identifying information ifthe target user has authorised the requester to initiate provision oflocation information that associates with the target user; and if therequester is authorised by the target user to initiate provision oflocation information that associates with the target user, initiatingthe provision of said location information.

According to another aspect of the present invention there is provided acommunication system comprising: a location information provisionentity; communication media for signalling from a client entity to thelocation information provision entity a request for location informationassociated with a target user, said request containing informationidentifying the requester of said location information; and verificationmeans for verifying based on said identifying information if the targetuser has authorised the requester, wherein provision of locationinformation that associates with the target user can be initiated onlyif such authorisation is given.

According to another aspect of the present invention there is provided alocation service server for use in a communication system, the locationservice server being arranged to receive a request for locationinformation associated with a target user, said request containinginformation identifying the requester of said location information andto verify based on said identifying information if the target user hasauthorised the requester, whereby the location service server authorisesprovision of location information that associates with the target useronly for requesters authorised the by the target user.

According to another aspect of the present invention there is provided auser equipment for communication via a communication system, the userequipment being arranged to receive and process messages that associatewith provision of information about the location of the user equipment,and to authorise provision of such information.

In a more specific form the request is generated at a user equipment ofthe requester and signalled to a location service client entity adaptedfor provision of location services for the users of the communicationsystem.

Location information associated with the target user may be providedonly for requesters who are determined by the target user as beingauthorised to receive information associated with the location of thetarget user.

At least a part of information about the authorisations by the targetuser may be stored in storage means provided in the communication systemand/or in a second communication system and/or at the user equipment ofthe target user.

The verification may comprise verifying if an identifier of therequester can be found from a list of identifiers associated with thetarget user.

Said identifying information may be signalled to the user equipment ofthe target user for the authorisation. The identifier information maycomprise n unique code or a name. The name may be in the form of acharacter string. Initiation of provision of location information maythen be authorised or denied at the user equipment of the target user inresponse to receiving said identifying information. The user of the userequipment may authorise requesters on a case by case basis.

An identifier may be translated to a format based on which theverification can be performed.

Information about the authorisations by the target user that is storedin storage means may be modified by means of the user equipment of thetarget user.

The embodiments of the invention may provide a user with a possibilityto allow or deny positioning requests from specific requesters. In someembodiments the determination may be done on a case by case basis. Thusthe privacy control of individual user may be enhanced. A list ofallowed requestors can be implemented in a secure environment, e.g. in atelephone operators network. The centralised storage of informationabout the authorised requesters may be used to prevent distributions ofthis information to several entities, such as to a plurality ofApplication Service Providers (ASPs). Instead, the information about theauthorised requesters may be kept unknown to the ASPs whereby the riskof misuse of this information can be reduced. Functions such as privacychecking and authorisation management may be concentrated into theoperator's domain.

BRIEF DESCRIPTION OF DRAWINGS

For better understanding of the present invention, reference will now bemade by way of example to the accompanying drawings in which:

FIG. 1 shows an embodiment of the present invention;

FIG. 2 is a signalling flowchart in accordance with an embodiment; and

FIG. 3 is a signalling flowchart in accordance with another embodiment.

DESCRIPTION OF PREFERRED EMBODIMENTS OF THE INVENTION

Before explaining possible operation in accordance with the principlesof the invention in more detail with reference to FIGS. 2 and 3, areference is made to FIG. 1 which is a simplified presentation of acellular system providing location services. It should be appreciatedthat even though the exemplifying telecommunications network shown anddescribed in more detail uses the terminology of the third generation(3G) UMTS (Universal Mobile Telecommunications System) public landmobile network (PLMN), the proposed solution can be used in any systemproviding mobile communications for users and some kind of locationinformation service. Examples of other telecommunications systemsinclude, without limiting to these, standards such as the GSM (GlobalSystem for Mobile communications) or various GSM based systems (such asGPRS: General Packet Radio Service), AMPS (American Mobile Phone System)or DAMPS (Digital AMPS), IMT 2000 (International MobileTelecommunications system 2000), i-phone and so on.

More particularly, FIG. 1 shows an arrangement in which base stations 3(only one shown for clarity) of the cellular system 1 provide radiocoverage areas i.e. cells 2. Each radio coverage area 2 is typicallyserved by a base station. It should be appreciated that one cell mayinclude more than one base station site. A base station apparatus orsite may also provide more than one cell. The shape and size of thecells 2 depend on the implementation and may be different from theillustrated shapes. The shape and size of the cells may also vary fromcell to cell. It should be appreciated that in some systems the basestation may be referred to as Node B.

Two user equipment such as mobile stations (MS) 6 and 7 are also shown.It shall be appreciated that typically a number of user equipment willbe in communication with each base station although only two userequipment 6 and 7 are shown in FIG. 1 for clarity. Each base station isarranged to transmit signals to and receive signals from the mobile userequipment (UE) 6 and 7 via a wireless interface. Likewise, the userequipment 6 and 7 are able to transmit signals to and receive signalsfrom the base stations.

Each of the base stations is connected to an access network controllersuch as a radio network controller (RNC) of a UMTS terrestrial radioaccess network (UTRAN). The radio network controller may be connected toappropriate core network entities of the cellular system, such as a MSC(mobile switching centre) and/or SGSN (serving general packet radioservice support node) 11, via a suitable interface arrangement. These,however, do not form an essential element of the invention and are thusnot explained in any greater detail.

The location of a mobile user equipment may vary in time as the userequipment is free to move within the coverage area of a base station andalso from a coverage area to another coverage area. The modemcommunication systems are capable of providing information regarding thegeographical location of a user equipment within the coverage areathereof. The geographical location may be defined on the basis of theposition of the mobile station relative to the base station(s) of themobile telecommunications network.

The geographical location of the user equipment may be defined, forexample, in X and Y co-ordinates or in latitudes and longitudes. Apossibility is to use the relation between defined radiuses and angles,e.g. based on the spherical coordinate system or alike. It is alsopossible to define the location of the base stations and/or mobilestations in vertical directions. For example, Z co-ordinate may be usedwhen providing the location information in the vertical direction. Thevertical location may be needed e.g. in mountainous environments or incities with tall buildings.

In FIG. 1 the location service (LCS) functionality of the communicationsystem is provided by a Gateway Mobile Location Center (GMLC) entity 10.The GMLC location service node 10 is for gathering and storing data thatis required for the provision of the location information. The locationservice node 10 is arranged to receive via appropriate interface meansinformation concerning the location of the mobile user equipment fromthe cellular system.

The cellular system may be provided with various different means forprocessing information gathered from the cells and/or some otherparameters and/or for computing by processor means appropriatecalculations for determining and outputting the geographical location ofthe target user equipment. The location information may be obtained byusing one or more of the appropriate location techniques. At least apart of the location information may be provided based on informationprovided by system that is separate from the communication system, suchas by means of the Global Positioning System (GPS) or similar. Sincethere are various possibilities how to implement the location servicesin the cellular system and since the invention is not dependent on theused location determination technology, these are not be described inany greater detail herein.

In order to be able to separate the user equipment from each other, thelocations service entity 10 is capable of processing at lest one form ofidentifiers. The identity information may be provided e.g. by means of amobile subscriber ISDN number (MSISDN), an international mobilesubscriber identifier (IMSI) or a temporary identifier (such as atemporary international mobile subscriber identifier TIMSI) of themobile user equipment, passwords, or any other form of identifier thatcan be reliably used for identifying a user equipment and/or a user.

The location service node may be implemented in the core network bymeans of a LCS server entity 10. The LCS server 10 is arranged toreceive location information from the radio access network viaappropriate controller entities such as the MSC and/or SGSN connected bythe appropriate interface means to the access network.

This location service node may provide the location information in apredefined manner to a location services (LCS) client 12. A LCS Client12 can be any entity that makes use of the location information. The LCSclient 12 can be seen as a logical functional entity that may make arequest to the location service entity 10 for the location informationof one or more target user equipment.

As shown by FIG. 1, the LCS client 12 may be an entity that is externalto the communication network 1, the client entity 12 being provided inan ASP domain 4. The LCS client may also be an internal client (ILCS)i.e. reside in any entity or node (including the mobile station) withinthe communication system 1.

The LCS clients are entitled to receive at least some degree ofinformation concerning the location (or location history) of a targetuser equipment. The particular requirements and characteristics of a LCSClient are typically known to the location service server of thecommunication system by its LCS client subscription profile. As will bedescribed in more detail below, particular restrictions associated witheach target user equipment may also be defined.

The location service server 10 may consist of components and bearersneeded to serve the LCS client 12. The server 10 may provide a platformwhich will enable the support of location based services in parallelwith other telecommunication services such as speech, data, messaging,other teleservices, user applications and supplementary services. TheLCS Server 10 may thus provide the client 12, on request orperiodically, the current or most recent geographic location (ifavailable) of the target user equipment or, if the location fails, anerror indication and optionally the reason for the failure. A moredetailed description of a LCS entity that may be employed in theembodiments of can be found e.g. from the above referenced 3GPPtechnical specification No. 3GPP TS23.271.

In FIG. 1 the LCS client 12 forms an entity that is capable of providingon request information concerning the geographical location of a targetuser equipment 6.

Such location information may be requested by clients such as the userequipment 7 (the requester). However, as explained in more detail below,the arrangement is such that a response is provided only to thoselocation requests that originate from a properly authorised clients ofthe LCS client 12. The provision may be initiated only if requirementsregarding the privacy of the target user equipment 6 are satisfied.

In accordance with an embodiment a separate network entity is providedfor the purposes of verifying if a requester is entitled to receivedlocation information regarding a specific target user equipment. Theparties of the location request (i.e. the requestor and the target) maybe identified based on appropriate identifiers. A possible identifiermay be based on a Mobile Subscriber ISDN (MSISDN) number that is uniquefor each mobile subscriber.

In FIG. 1 the verification function is provided by a network serverentity 14 referred to as a Location Middleware. The server entity 14 isprovided in the core network side of the communication system 1. TheLocation Middleware server entity 14 is for handling the requestsreceived from the LCS client application 12 and for deciding how toproceed with the requests. The server 14 has advanced control functionto send the request to different types of location servers (e.g. theGMLC node 10).

This server entity 14 may also provide control of features such asSubscriber Privacy, Subscriber Authentication, System Control and SystemOperations functions. The Location Middleware server allows servicelevel separation to ensure privacy of the subscribers and to enableverification of the service requesters.

The server entity 14 is shown to comprise a database 18 for storing alist 19 wherein target user equipment identities and allowed userequipment identities are associated to each other. That is, the database18 provided a link between the target user equipment 6 (and this theuser thereof) and any user equipment that is allowed by the user of thetarget user equipment to receive location information concerning thetarget user equipment 6.

The target user equipment 6 may be provided with a user interface andother necessary means for modifying the list restrictions. For example,the target user equipment may be arranged to display a menu for the userby means of which the user may add a name or user equipment identifierto the list 19 or remove a name or user equipment identifier from thelist 19. According to a possibility the list can be managed by accessinga management document in a web server.

The server is also shown to include a requester check function 20. Anickname translation function 22 is shown to be associated with thecheck function 20. Example of the operation of these entities will bedescribed in the following with reference to FIGS. 2 and 3.

It shall be appreciated that the separate verification server 14 is nota necessity. At least a part of the functions of the server entity 14may be provided by the location service entity 10. For example, thefunctionality of checking if the “Requester” is authorised or not may beprovided by mean of the GMLC holding also the “Authorized UE List”discussed above. Therefore the Location Middleware of the FIG. 1embodiment may also be seen as a logical functionality that is not tiedto any physical element of the network.

In accordance with an embodiment shown in FIG. 2 the originator of arequest i.e. the requester user equipment 7 signals a service requestfor information regarding the location of the target user equipment 6.An identifier parameter is added in an appropriate element of therequest, the request thus containing an identifier such as the MSISDN ora nickname of the requester.

The identifier parameter identifying the requester is passed to thelocation service entity 10 form the LCS client 12. Based on the identityinformation the requester may be checked by the check function 20against the list 19 of authorised requesters in the database 18. If theidentifier is among the authorised identities which are allowed toreceive information regarding the target user equipment determinationsregarding the location of the target user equipment are allowed toproceed and a response is generated. If not, the request is denied andan appropriate procedure follows. For example, an error message, orrequest denied message may be sent to the LCS client.

If a nickname or similar is used, the nickname translation function 22may be needed to translate the identifier into a form that can beverified against the list 19 stored in the database 18.

The identifier may be added to all location requests between a LCSClient 12 and a LCS Server entity 10, such as the GMLC. The identifiermay be added to the request by the requesting user equipment 7 or by theLCS client 12.

Capacity to carry the identifier parameter may be added to a protocoldefining the so called Le interface between the GMLC 10 and a locationserver client entity 12. The current Le interface is described moredetail e.g. in the above referenced 3GPP Technical Specification 23.271.

FIG. 3 shows another embodiment wherein a target user equipment 6 isenabled to authorise the provision of the location information incase-by-case basis. In here a message containing information about theidentity of the requester may be sent to the target user equipment 6. ALCS Client ID may also be included in this message for added privacy.The target user may then allow or deny a positioning request on case bycase basis.

Identifier such as the MSISDN or similar unique identifier may beforwarded to the target user equipment 6 as a part of a LCS Clientnotification message. A possibility is to associate the identifierinformation with the name of the requester at the target user equipment.The identifier information may for example be directed to the phone bookof the target user equipment 6 so that the MSISDN is translated into aname based on a phone book entry. Now the user has the possibility toallow or deny the positioning request based on actual requestorinformation.

Said Information about the requester may also comprise the name ornickname of the requester. The name may be included into the message tothe target user equipment either instead or in addition to otheridentifiers, such as the MSISDN. The target user equipment 6 may thendisplay the name directly as indicated by the message.

A specific client name parameter referred to as ‘client name’ may beadded to the message. The client name parameters as such is known fromother applications, and has been proposed to be used in variousstandards. It is therefore not explained in any great detail herein. Itis sufficient to note that the client name parameter may consists of atext string. For example, GSM release 98 defines a client name parametercapable of containing a text string of the maximum length of 63characters. Since substantially long character strings are possible, theclient name parameter may include both the name or the requester and thename of the LCS client.

The parameter including the name of the requester is preferably includedinto the message by the LCS client 12. The parameter may then betransported via the so called Le interface between the LCS client 12 andthe LCS server 10. The parameter may then be transported via the socalled Lg interface between the LCS server 10 and the radio network ofthe communication system serving the target user equipment and furtherto the target user equipment 6.

According to a possibility the name/nickname is already inserted in therequest at the requester user equipment 7. The requester user equipmentmay accomplish this automatically, or the user thereof may input hisname. For added security, the LCS client 12 or any other appropriateentity at the network may verify the name.

The target user equipment may prompt the user and ask form his/hersconfirmation whether the request should be approved or not. According toa possibility the user equipment responds automatically based oninformation regarding authorised/non-authorised requesters stored in thedatabase thereof.

In the FIG. 3 embodiment a verification is not necessarily needed at thenetwork. Instead, the identity of the requester may be added to anotification sent to the target user equipment 6 and the authorisationmay be done at the target user equipment. However, a verification basede.g. on the list 19 of FIG. 1 may still be used in here e.g. forimproved safety thereby providing a double check feature. The targetuser may also wish to receive the notifications e.g. only on certaintimes while at the rest of the times he/she may wish to rely on theauthorisation list.

The processing of the requests and authorisations may need addition of anotification processing capability at the target user equipment 6.However, this is an implementation issue, and may be accomplished bymean of the existing processor and data processing hardware of the userequipment, and will thus not be discussed any more detail herein.

In the above the identifier was described as being on the MobileSubscriber ISDN (MSISDN) number of the user. Other possibilities for theunique identifier include the IMSI, TIMSI, password, and so on. Inprinciple the identifier may be any anything as long as it can beprocessed by the PLMN system so that the verification can be made basedon it.

Responses by the LCS client 12 to location information requests may havethe form of simple coordinate (x, y) information or contain more valueadded services like a reverse-geocoded response provided with a streetname or a map reference. The response may even comprise a map and apointer on the map.

For Emergency and Lawful intercept location services this parameter maynot be needed depending on local legislation. The authorisation functionmay be overrode e.g. if the request comes from an emergency service.

It should be appreciated that the elements of the location servicefunctionality may be implemented anywhere in the telecommunicationssystem. The location service implementation may also be distributedbetween several elements of the system. Furthermore, although the abovedescribes embodiments employing a specific LCS client node, this is nota necessity. The request for location information may be addresseddirectly to a location service entity of the communication system, suchas to the GMLC or any other element associated with the provision oflocation information. If a LCS client is used, it does not need to be anexternal element, but may also be implemented within the communicationnetwork and/or be run the by the operator of the network.

According to an embodiment the target user equipment 6 itself providesat least part of the information required by the LSC client, that is atleast a part of the information is provided directly by the target userequipment instead of e.g. the GMLC. The user equipment 6 may be providedwith the location service processing function and is capable ofgenerating and transporting location information thereof to the clientsvia the core network and/or the LSC server.

According to an embodiment a plurality of target user equipment isgrouped into one or more “location service groups”, each of these groupsbeing provided with an unique identifier that may then be used forpreventing unauthorised provision of location information regarding anymember of the group. The group may consist of subscribers that are of apredefined type, such as personnel of an organisation, members of afamily or any other group of users that may be grouped together based onan appropriate criteria and may have similar needs regarding theselective prevention of location information provision.

It should be appreciated that whilst embodiments of the presentinvention have been described in relation to user equipment such asmobile stations, embodiments of the present invention are applicable toany other suitable type of user equipment.

The embodiment of the present invention has been described in thecontext of a third generation communication system. This invention isalso applicable to any other communication system.

It is also noted herein that while the above describes exemplifyingembodiments of the invention, there are several variations andmodifications which may be made to the disclosed solution withoutdeparting from the scope of the present invention as defined in theappended claims.

1-21. (canceled)
 22. A method in a communication system, the methodcomprising: signaling to a location middleware server entity a requestfor location information associated with a target user, said requestcontaining information identifying the requestor of said locationinformation; verifying based on said identifying information if thetarget user has authorized the requester to initiate provision oflocation information that associates with the target user; and if therequester is authorized by the target user to initiate provision oflocation information that associates with the target user, sending saidrequest from said middleware server entity to a location service serverentity, wherein said request is signaled to said location middlewareserver entity other than via said location server entity.
 23. A methodas claimed in claim 22, wherein the request is generated at a userequipment of the requester and the location service server entity is aGateway Mobile Location Centre.
 24. A method as claimed in claim 22,wherein location information associated with the target user is providedonly for requesters who are determined by the target user as beingauthorized to receive information associated with the location of thetarget user.
 25. A method as claimed in claim 22, wherein at least apart of the information about the authorizations by the target user isstored in storage means provided in the communication system.
 26. Amethod as claimed in claim 22, wherein the at least a part ofinformation about the authorizations by the target user is fetched froma second communication system, said second communication system beingaccessible for the entities of the communication system wherein theverification is performed.
 27. A method as claimed in claim 25, whereina verification entity of the communication system accomplished theverification based on said stored information and identifyinginformation.
 28. A method as claimed in claim 22, wherein theverification comprises verifying if an identifier of the requester canbe found from a list of identifiers associated with the target user. 29.A method as claimed in claim 22, comprising signalling of saididentifying information to the user equipment of the target user for theauthorization.
 30. A method as claimed in claim 29, wherein initiationof provision of location information is authorized or denied at the userequipment of the target user in response to receiving said identifyinginformation.
 31. A method as claimed in claim 29, wherein informationabout the authorizations by the target user is stored in storage meansprovided at the user equipment of the target user, and wherein the userequipment verifies based on the received information if the storagemeans of the user equipment contains an authorization for the requester.32. A method as claimed in claim 29, wherein said identifyinginformation comprises the name or nickname of the requester.
 33. Amethod as claimed in claim 32, wherein the name or nickname is containedin a client information parameter.
 34. A method as claimed in claim 29,wherein the user of the user equipment authorizes the requester on acase by case basis.
 35. A method as claimed in claim 22, comprisingtranslation of an identifier to a format based on which the verificationcan be performed.
 36. A method as claimed in claim 22, comprisingmodifying information about the authorizations by the target user thatis stored in storage means by means of the user equipment of the targetuser.
 37. A communication system comprising: a location service serverentity; a location middleware server entity; communication media forsignalling from a client entity to the location middleware server entitya request for location information associated with a target user, saidrequest containing information identifying the requester of saidlocation information; and verification means for verifying based on saididentifying information if the target user has authorized the requester,wherein said request for location information is from said locationmiddleware server entity sent to said location service server entityonly if such authorization is given, wherein said request is signaled tosaid location middleware server entity other than via said locationservice server entity.
 38. A location middleware server for use in acommunication system, the location middleware server being arranged toreceive a request for location information associated with a targetuser, said request containing information identifying the requester ofsaid location information and to verify based on said identifyinginformation if the target user has authorized the requester, whereby thelocation middleware server sends said request for location informationto a location service server only for requesters authorized by thetarget user, and wherein said request is signaled to said locationmiddleware server entity other than via said location service serverentity.
 39. A user equipment for communication with a locationmiddleware server via a communication system, the user equipment beingarranged to receive and process messages that associate with requestsfor the provision of information about the location of the userequipment, and to send to said location middleware server messagesauthorizing the transmission of said requests from said locationmiddleware server to a location service server, wherein said request issignaled to said location middleware server entity other than via saidlocation service server entity.
 40. A user equipment as claimed in claim39, comprising a user interface arranged to enable the user to authorizeor deny requests for location information and/or for modifyinginformation regarding authorizations stored in a storage means.
 41. Asystem according to claim 37, wherein the location service server entityis a Gateway Mobile Location Centre.
 42. A location middleware serveraccording to claim 38, wherein the location service server is a GatewayMobile Location Centre.
 43. A user equipment according to claim 39,wherein the location server entity is a Gateway Mobile Location Centre.